CA ARCserve® D2D r16.5 Update 2 Release Notes
1.0 Welcome
2.0 Enhancements
3.0 Issues Fixed
4.0 Known Issues
5.0 Limitations
6.0 Installation
6.1 Prerequisite Tasks
6.2 Installation Instructions
7.0 Contact Arcserve
1.0 Welcome
Welcome to the CA ARCserve D2D r16.5 Update 2 Release
Notes. This Release Notes contains important information
about this update.
2.0 Enhancements
The following enhancements have been added to CA ARCserve
D2D for this update:
- Support is added for the following:
- Microsoft SQL Server 2014
- Microsoft Exchange 2013 SP1
- VMware vSphere 5.5 Update 1
- VMware VDDK 5.5 Update 1
- The default version of VMware VDDK that is shipped with CA
ARCserve D2D has changed.
- x64 OS - VMware VDDK 5.5 Update 1
- x86 OS - VMware VDDK 5.1 Update 2
Note: As per VMware Compatibility, it is required to have
VIX 1.13 installed on Virtual Standby and Host Based VM
Backup proxies.
- Test Fixes installed. For more information, see Issues
Fixed in the Release Notes.
3.0 Issues Fixed
This update fixes the following issues, which could have
occurred:
- Provides access for CA ARCserve D2D r16.5 Update 1 Release
Notes. (Test Fix RO61712)
- A problem where the CA ARCserve D2D UI does not open after
upgrading from CA ARCserve D2D r16.5 to CA ARCserve D2D
r16.5 Update 1. This problem is seen when CA ARCserve D2D
r16.5 is installed from the ISO image. (Test Fix RI62075)
- A problem that corrects a security vulnerability when
integrating CA ARCserve D2D with CA ARCserve Backup. (Test
Fix RI64264, T5LE133)
- Provides access for vCenter Appliance support with CA
ARCserve Central Host-Based VM Backup. (Test Fix RO65682,
T55Z004)
- Provides support for Windows 2012 r2 to CA ARCserve Central
Applications and CA ARCserve D2D. (Test Fix RO66936,
T55U012)
- Provides support for VMware vSphere 5.5 and VDDK 5.5. This
patch also adds support for VIX 1.13.0. (Test Fix RO68430)
- A problem that can arise from the "HeartBleed" security
vulnerability. (Test Fix RO69431)
- A problem where a backup job crashes when starting up.
(Test Fix T5LE125)
- A problem when you attempt to run the pre flight check,
that causes the application to return the following error
message:
"Unable to retrieve information about the application. This
can prevent application level backups from completing
successfully."
This problem occurs when the C: volume does not exist on
the guest system. (Test Fix T36A814)
- A problem when a merge job fails near the end of its task,
that causes the application to return the following message
in the activity log:
"Error: JobXXXXXXXX - Failed to delete file <path to the
file>. Error code: -1"
This problem does not occur on all machines, but usually
occurs on some particular machines. (Test Fix T245849)
- A problem when you attempt to perform a bare metal recovery
on Windows XP SP3, that causes the recovery to fail on the
C drive and causes the application to return the following
error message in the log file:
"Get bootcode filename failed, resource id 65535". (Test
Fix T36A819)
- A problem that causes a virtual standby conversion job to
fail with the following error message:
"Failed in removing and adding disks for the virtual
machine [VM_NAME]". (Test Fix T2D2987)
- A problem where a blank screen displays in the browser
when trying to open the CA ARCserve D2D console after
applying the r16.5 Update1 patch RO61712. When this problem
occurs, it is observed that some files in the following
paths have been set to Read Only :
- \Program Files\CA\ARCserve
- D2D\TOMCAT\webapps\ROOT\contents
- \Program Files\CA\ARCserve
- D2D\BIN\VDDK\Bin\VDDK64\bin
- \Program Files\CA\ARCserve
- D2D\BIN\VDDK\Bin\VDDK64\plugins (Test Fix T245856)
- A problem that after upgrading CA ARCserve D2D from r16.0
to r16.5, the file copy job fails. The Amazon CCI log shows
the following error status code of 403:
"The request signature we calculated does not match the
signature you provided. Check your key and signing method."
This only occurs when CA ARCserve D2D is integrated with
N-able Technologies N-central. (Test Fix T2D2993)
- A problem that causes the CA ARCserve D2D web service to
crash when you set the Exchange restore option on the GUI.
(Test Fix T5LE134)
- A problem where a Virtual Standby Conversion Job fails with
the following error message:
Error: Job0000027F - Failed to create the bootable
snapshot. Snapshot name is S0000000290_bootable. (Test Fix
T55Z001)
- A problem that when running a CA ARCserve D2D SQL backup
with the purge transaction log option enabled, causes the
MS SQL databases recovery mode to change from simple to
full after the backup. (Test Fix T36A825)
- A problem where the Last Successful Event for a Copy
Recovery Point job in the CA ARCserve D2D home page UI
(under the Protection Summary) does not get updated even
when it completes successfully. (Test Fix T55Z002)
- Provides support for VMware VIX 1.12. (Test Fix T55Z006)
- A problem that causes the CA ARCserve D2D merge backup
session to fail with the following error:
"[CMergeUtil::GetBackupInfo] Failed to read backupinfo.xml.
(Path=[\\xxxxx})"
The backupinfo.xml file has an extra null character at end,
the xml API is unable to process the file. (Test Fix
T55Z007)
- A problem that causes a CA ARCserve D2D backup to fail with
the following error to an iOmega NAS device:
"Error: Job00000xxx - Operations (create, close,read,
write) on file
\\xx.xx.xx.xx\machinename\VStore\S0000000001\disk2
754413731.D2D.idx failed, Error code:5,[Access is denied]."
(Test Fix T55Z010)
- A problem that prevents the following message to be output
on an Italian OS durig a merge job, which then causes the
merge process to hang:
"A total of xxxMB unique data will be merged." (Test Fix
T55Z011)
- Provides support for VMware vSphere 5.5 and VDDK 5.5. This
patch also adds support for VIX 1.13.0. (Test Fix T55Z017)
- A problem where the Bootkit wizard always aborts without
displaying any error when it is creating the bootable BMR
image. This problem is observed on Windows 2003 (x86, x64
versions). (Test Fix T245870)
- A problem where the SBS Server could freeze when CA
ARCserve D2D generates the Exchange GRT Catalog. (Test Fix
T55U010)
- A problem that causes a CA ARCserve D2D merge to fail with
the following error in afstor.log:
"Check header magic error, hdr.Magic = 8676594127358291811.
file:\\svfs02.suhrkamp.intranet\d2d$\SVMGMT02\VStore\S0000000144\disk2927994450.D2D"
This problem occurs when backing up with no compression, no
encryption, and integrating CA ARCserve D2D and CA ARCserve
Backup. (Test Fix T55Z019)
- A problem where you are unable to set Amazon cloud as the
file copy destination, and information is not saved after
clicking the Save button. (Test Fix T5TM145)
- A problem that when you create a BMR ISO image, it fails if
ADK 8.1 is installed. (Test Fix T36A844. T36A852)
- A problem where the file copy size is incorrect. The
Protection Summary Total Size for file copy is recorded
with the uncompressed size, not the compressed size stored
on the cloud.
Note: After applying the fix, it will record the future
file copy size with the compressed size information.
However, the size already recorded cannot be changed. So,
the Protection Summary may still show the large size. The
activity.log records the actual size stored on the cloud
for this particular file copy job, "Total data size written
to File Copy destination is xx MB." (Test Fix T55Z021)
- A problem that causes the following error when restoring an
Exchange DB to RSG:
"Job00000xxx - Failed to restore the File. (File
[x:\mountpoint\mountpoint\LOGS3], Error [The system cannot
find the path specified.])." Where x:\mountpoint\ is a
mount point to external storage. (Test Fix T55Z022)
- A problem that causes the following incorrect VMImage.log
message during a restore:
"Failed to open file[Z:\filename.doc] error[3]"
The message is written to the log file even thought the
file is restored successfully. After applying this fix, the
message will be printed if the restore was not successful.
(Test Fix T55Z023)
- A problem that prevents you from opening CA ARCserve D2D
from the tray monitor. No error is displayed. This problem
is due to not enough storage available to process the
command. (Test Fix T55U015)
- A problem where CA ARCserve D2D reports a file read error
59 when running a backup job. (Test Fix T5LE138)
- A problem where CA ARCserve D2D reports error 64 and error
59 when running a backup or a Virtual Standby conversion.
(Test Fix T5LE139)
- A problem that causes a CA ARCserve D2D backup job to crash
while collecting DR Information. (Test Fix T5LE141)
- A problem where a CA ARCserve D2D incremental backup job
crashes when there is an invalid GPTPartitionName in
AdrConfigure.xml. (Test Fix T5TM162)
- A problem that addresses a security vulnerability within CA
ARCserve D2D. (Test Fix T55Z028)
- A problem with a server crash or BSOD (blue screen of
death) that occurs with a kernel stack overflow. (Test Fix
T55U019)
- A problem that after Virtual Standby conversion, the VM
cannot start up and will receive a blue screen with an
error code 0x7B when a driver is needed for the SCSI disk
on the source machine. (Test Fix T5TM163)
- A problem where a CA ARCserve D2D incremental backup job
crashes right after the job starts. The crash occurs in
AFVolumeParse.dll. (Test Fix T5LE142)
- A problem where a CA ARCserve D2D merge fails with error
code 6 in AFStor.Log. (Test Fix T5LE143)
- A problem where a CA ARCserve D2D restore fails with error
code 32 when the restore location already has the same file
there. (Test Fix T5LE144)
- A problem with restoring Exchange Mail where the login
failed. The problem happens on the GRT restore validation
screen and displays the following message:
"Login failed: Please ensure that user account has all the
necessary permissions for restore." (Test Fix T5LE145)
- A problem where AFUtil.exe prints the parameters specified
by /pwd and /upwd to afutil.log. (Test Fix T245885)
- A problem where during a BMR, the machine can receive a
BSOD (blue screen of death) during start up. This could
happen if the target machine has a larger disk than the
source machine. (Test Fix T55U021)
- A problem where a CA ARCserve D2D copy session job crashes.
(Test Fix T5TM167)
- A problem where the database recovery model changes from
full to simple and from simple to full during the backup
time, which could cause potential data loss. (Test Fix
T36A857)
- A problem where a CA ARCserve Central Host-Based VM Backup
backup will always perform a full backup even though an
incremental backup was specified. (Test Fix T2D2954)
- A problem where the backup of some VM machines through CA
ARCserve Central Host-Based VM Backup, receive the
following warning message:
"Could not get volume information from virtual machine
guest OS".
The result is that the catalog is not created for the VM,
and therefore file level restores are not possible. (Test
Fix T2D2971)
- A problem where a CA ARCserve D2D restore from the cloud
displays the following message:
"Catalog data for the selected destination is not
available. Click Sync to submit a catalog synchronization
job".
The time to perform this job may take a long time. This fix
will use multithread to sync the job which improves the
performance. The default thread number is 4. You may change
this to any number by creating a DWORD value
ThreadForCatalogSync under
HKEY_LOCAL_MACHINE\SOFTWARE\CA\CA ARCserve
D2D\AFArchiveDll. The maximum value is 10. (Test Fix
T2D2982)
- A problem during a BMR, where the machine could receive a
BSOD during start up. This would happen if the target
machine has a larger disk than the source machine. (Test
Fix T55U021)
- A problem in Cloud Configuration for a copy job, where
"Test Connection" fails if the proxy server uses the Basic
method for authentication. (Test Fix T245831)
- A problem in a BMR for a Windows Server 2012 server with
UEFI, in the Express mode, the generated partitions have a
different order as they are in the source VM. In advanced
mode, the recovery partition is not generated
automatically. (Test Fix T5TM103)
- CA ARCserve D2D backed-up data corruption may happen for
various reasons. To help you determine if you have data
corruption, the AFUtil.exe utility was created. The
AFUtil.exe utility is used to scan a CA ARCserve D2D backup
session to confirm the integrity of the backed-up data.
If you have determined that the existing recovery points in
your environment have been affected (with data corruption)
and no good Full backup exists after these corrupted
recovery points, you must run a Full Backup to restart the
recovery point chain or configure a recovery set to run a
Full backup regularly.
This utility should be placed in the "Bin" folder for the
CA ARCserve D2D installation prior to using it. When this
utility is executed without any parameters, by default it
will determine the configured backup destination and scan
the oldest Full Backup session of all the machines that are
protected by CA ARCserve D2D. However, it is strongly
recommended to scan all backup images to ensure that data
from these recovery points are restorable.
Because this utility performs a complete scan of your
backed-up data for the selected recovery point, this can be
a time-consuming process. The utility cannot run if other
jobs are running at the same time. Verify that the CA
ARCserve D2D Web Service is stopped and that there are no
active jobs running. (Test Fix RO57870)
- A problem where all CA ARCserve D2D backups show as
Incremental even though a Full backup does exist. This is
caused by an incorrect backup type in BackupInfo.xml under
the Full backup session, which causes there to be no Full
backups displaying under the CA ARCserve D2D home page.
After this fix is applied, running a new merge job to run
will correct the BackupInfo.xml to have a Full backup type
for the Full session. (Test Fix T2D2966)
- A problem where a backup fails with error code 64 and
displays the following message:
"Can't find file: error=64,trying to find .VHD file
CDescFile::AddMetaDataSection: WriteFile failed. err[6]"
(Test Fix T5LE123)
For all issues fixed in this release, see the CA ARCserve
D2D r16.5 Release Notes.
4.0 Known Issues
This update includes the following known issues, which
could have occurred:
For all known issues in this release, see the CA ARCserve
D2D r16.5 Release Notes.
5.0 Limitations
For all limitations in this release, see the CA ARCserve
D2D r16.5 Release Notes.
6.0 Installation
The following sections provide information about
installation prerequisites and installation instructions.
6.1 Prerequisite Tasks
Consider the following prerequisite tasks before installing
this update:
- Before you install this update, verify that CA ARCserve D2D
r16.5 or CA ARCserve D2D r16.5 Update 1 is installed.
6.2 Installation Instructions
You can use two methods to install this update:
Note: The D2D probe is available for download and
installation from the Nimsoft Internet Archive.
7.0 Contact Arcserve
Contact Arcserve Support
For your convenience, Arcserve provides one site where you
can access the information that you need for your Home
Office, Small Business, and Enterprise Arcserve products.
At http://arcserve.com/support, you can access the
following resources:
- Online and telephone contact information for technical
assistance and customer services
- Information about user communities and forums
- Product and documentation downloads
- Arcserve Support policies and guidelines
- Other helpful resources appropriate for your product
Providing Feedback About Product Documentation
If you have comments or questions about Arcserve product
documentation, you can send a message to techpubs@arcserve.com.
Copyright © 2014 Arcserve. All rights reserved. All
trademarks, trade names, service marks, and logos
referenced herein belong to their respective companies.